This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@cloudflare/[email protected]

Minor Changes

• #10048 dbdbb8c Thanks @vicb! - pass the compatibility date and flags to the unenv preset

• #10078 5991a9c Thanks @vicb! - add support for the native http modules

Patch Changes

• #10096 687655f Thanks @vicb! - bump unenv to 2.0.0-rc.19

[email protected]

Patch Changes

• #10081 defea6f Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  create-react-router	7.7.0	7.7.1

• #10082 2f3f090 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  create-qwik	1.14.1	1.15.0

• #10083 6d83a87 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  create-astro	4.12.1	4.13.0

• #10085 99b8eab Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  sv	0.8.18	0.8.20

[email protected]

Patch Changes

• #10075 82a5b2e Thanks @vicb! - fix the type of ForwardableEmailMessage

• #10058 f8f7352 Thanks @edmundhung! - fix: service binding fetch over dev registry should work without host header

• #9968 2df1d06 Thanks @dependabot! - chore: update dependencies of "miniflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20250712.0	1.20250726.0
  @cloudflare/workers-types	^4.20250712.0	^4.20250726.0

@cloudflare/[email protected]

Patch Changes

• Updated dependencies [82a5b2e, f8f7352, 2df1d06]:
  • [email protected]

@cloudflare/[email protected]

Patch Changes

• #10048 dbdbb8c Thanks @vicb! - pass the compatibility date and flags to the unenv preset

• #10096 687655f Thanks @vicb! - bump unenv to 2.0.0-rc.19

• #10040 26ffa05 Thanks @CarmenPopoviciu! - feat(vite-plugin): Add containers support in vite preview

  Adds support for Cloudflare Containers in vite preview. Please note that at the time of this PR a container image can only specify the path to a Dockerfile. Support for registry links will be added in a later version.

• #10054 bc910f9 Thanks @eltigerchino! - Add worker to the default conditions for resolving packages

  This makes it consistent with the conditions used when bundling Worker code with Wrangler.

• #10061 f8a80a8 Thanks @emily-shen! - fix: properly set the socket path that the container engine is listening on.

  Previously, this was only picking up the value set in Wrangler config under dev.containerEngine, but this value can also be set from env vars or automatically read from the current docker context.

• Updated dependencies [82a5b2e, f8f7352, 2df1d06, f8a80a8, dbdbb8c, 5991a9c, 687655f, 755a249]:

  • [email protected]
  • [email protected]
  • @cloudflare/[email protected]

@cloudflare/[email protected]

Patch Changes

• #10033 f467415 Thanks @pombosilva! - Make vitest-pool-workers not break when a Workflow binding script_name matches its Worker name

• Updated dependencies [82a5b2e, f8f7352, 2df1d06, f8a80a8, dbdbb8c, 687655f, 755a249]:

  • [email protected]
  • [email protected]

[email protected]

Patch Changes

• #10061 f8a80a8 Thanks @emily-shen! - feat(containers): try to automatically get the socket path that the container engine is listening on.

  Currently, if your container engine isn't set up to listen on unix:///var/run/docker.sock (or isn't symlinked to that), then you have to manually set this via the dev.containerEngine field in your Wrangler config, or via the env vars WRANGLER_DOCKER_HOST. This change means that we will try and get the socket of the current context automatically. This should reduce the occurrence of opaque internal errors thrown by the runtime when the daemon is not listening on unix:///var/run/docker.sock.

  In addition to WRANGLER_DOCKER_HOST, DOCKER_HOST can now also be used to set the container engine socket address.

• #10048 dbdbb8c Thanks @vicb! - pass the compatibility date and flags to the unenv preset

• #10096 687655f Thanks @vicb! - bump unenv to 2.0.0-rc.19

• #9897 755a249 Thanks @edmundhung! - fix: wrangler types should infer the types of the default worker entrypoint

• Updated dependencies [82a5b2e, f8f7352, 2df1d06, dbdbb8c, 5991a9c, 687655f]:

  • [email protected]
  • @cloudflare/[email protected]

@cloudflare/[email protected]

Patch Changes

• #10061 f8a80a8 Thanks @emily-shen! - feat(containers): try to automatically get the socket path that the container engine is listening on.

  Currently, if your container engine isn't set up to listen on unix:///var/run/docker.sock (or isn't symlinked to that), then you have to manually set this via the dev.containerEngine field in your Wrangler config, or via the env vars WRANGLER_DOCKER_HOST. This change means that we will try and get the socket of the current context automatically. This should reduce the occurrence of opaque internal errors thrown by the runtime when the daemon is not listening on unix:///var/run/docker.sock.

  In addition to WRANGLER_DOCKER_HOST, DOCKER_HOST can now also be used to set the container engine socket address.